Consume the editor from paranext-core's staged copy - #119

This package pinned @eten-tech-foundation/platform-editor ~0.8.13 and
scripture-utilities ~0.1.6 from the npm registry. Those packages are no longer published
from the repository we develop them in: scripture-editors now lives at
paranext/scripture-editors, and paranext-core builds it from source and stages the result
into dev-packages/staging/ rather than installing it from npm. Left as registry pins,
this package would stay frozen at whatever ETEN last published.

Points both at paranext-core's staged copy, matching how this repo already consumes
platform-bible-react, platform-bible-utils, and papi-dts from a sibling paranext-core
checkout.

package-lock.json is deliberately not updated here — regenerating it requires a
paranext-core that already carries the staging change, so it should be refreshed once
that has merged.

The editor `file:` specifiers point into paranext-core's
`dev-packages/staging/`, which is gitignored there and produced by core's
`preinstall`. Checking core out does not create it, and both workflows
install this repo before core and then install core with
`--ignore-scripts`, which skips that `preinstall`. npm links a missing
`file:` target and exits 0, so CI would have installed against a broken
symlink and failed later as an unresolved module. Stage core's dev
packages first instead; the script needs only git and node, which is why
core can run it as its own `preinstall`.

The lockfile drops the editor's transitive closure because npm resolves a
`file:` target's dependencies only when the target is inside the consuming
project's root, and core is a sibling. Those dependencies resolve through
the symlink's realpath from core's own `node_modules`, as this repo's
existing `file:../paranext-core/lib/...` dependencies already do.

Verified with an updated core beside it: lint clean, and both webpack
bundles compile.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017jvJ2eYTfxJaBkKoQbVeiW

The staging step ran `node .erb/scripts/stage-dev-packages.ts`, so eight repos
depended on the location of a file inside paranext-core; renaming or moving it
would have broken all of them at once, silently, since nothing here references
it in a way a search from core would find.

`npm run stage-dev-packages` is core's own entry point for the same thing. It
needs nothing installed, so it still works before core's `npm ci`, and it
survives the file moving. Core's script also carries
`--experimental-strip-types`, which is what lets a repo whose Volta pin predates
Node 22.18 run it at all.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TqDvvB9RpsxEE49f75ZtB6

paranext-core's postinstall checks that the staged editor packages match
core's package-lock.json. This repo installs core with
`npm ci --ignore-scripts` - required, because core's postinstall builds an
Electron DLL this repo has no use for - so that check never ran here, and a
build could resolve the editor from whatever the pinned branch happened to
hold at that moment.

`npm run verify:dev-packages`, added in paranext-core#2745, is that check on
its own. It reads the tree and reports; it never installs or repairs anything.

Also refreshes package-lock.json against core's current tree.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TqDvvB9RpsxEE49f75ZtB6